View-based expiration of shared content

ABSTRACT

Techniques related to view-based expiration of shared content are described. An online content management system receives a view access request from a client device. The view access request includes a shared link to a server-stored content item. A view access counter associated with the shared link is used to determine that the view access request is authorized. The shared link is resolved to the server-stored content item, and at least a portion of the server-stored content item is sent to the client device. Optionally, instructions that cause the client device to send an acknowledgement can also be sent to the client device. The acknowledgement indicates that one or more presentation conditions have been satisfied. The one or more presentation conditions can include presenting at least the portion of the server-stored content item at the client device. The online content management system receives the acknowledgement and increments the view access counter.

CROSS REFERENCE TO RELATED APPLICATIONS; BENEFIT CLAIM

This application claims the benefit as a Continuation of applicationSer. No. 14/983,168, filed Dec. 29, 2015 the entire contents of which ishereby incorporated by reference as if fully set forth herein, under 35U.S.C. § 120. The applicants hereby rescind any disclaimer of claimscope in the parent application or the prosecution history thereof andadvise the USPTO that the claims in this application may be broader thanany claim in the parent application.

TECHNICAL FIELD

The present Application relates to content collaboration technology.More specifically, the example embodiment(s) of the present Applicationrelate to view-based expiration of shared content.

BACKGROUND

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

Content sharing typically relies on one medium for sharing content andanother medium for communicating receipt of the shared content. Forexample, a sending entity can send a large file to a receiving entityvia a particular web-based service, but the sending entity and thereceiving entity may be unable to otherwise communicate via theparticular web-based service. Thus, the receiving entity may have toacknowledge receipt via a different web-based service. As a result, boththe sending entity and the receiving entity may leave and neglect toreturn to the particular web-based service, thereby causing theparticular web-based service to lose hard-won visitor traffic.Furthermore, communicating receipt of shared content often conveyslittle useful information. Such communications typically indicatenothing other than a successful transmission of the shared content.

BRIEF DESCRIPTION OF THE DRAWINGS

The example embodiment(s) of the present invention are illustrated, byway of example and not limitation, in the accompanying drawings in whichlike reference numerals refer to similar elements and in which:

FIG. 1 depicts an example computer architecture upon which embodimentscan be implemented.

FIG. 2 depicts an example client device.

FIG. 3 depicts an example request to create a shared link.

FIG. 4 depicts an example online content management system.

FIG. 5 depicts an example view access request.

FIG. 6 depicts an example mapping between links and view accesscounters.

FIG. 7 depicts an example data exchange that follows view accessauthorization.

FIG. 8 depicts a detailed view of an example acknowledgement sent to anonline content management system.

FIG. 9 depicts an example notification associated with a link sharer'saccount.

FIG. 10 is a flow diagram that depicts an approach for managing accessto shared content.

FIG. 11 is a very general block diagram of a computing device in whichthe example embodiment(s) of the present Application may be embodied.

FIG. 12 is a block diagram of a basic software system for controllingthe operation of the computing device.

DESCRIPTION OF THE EXAMPLE EMBODIMENT(S)

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the example embodiment(s) the present Application. Itwill be apparent, however, that the example embodiment(s) can bepracticed without these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order to avoidunnecessarily obscuring the example embodiment(s).

General Overview

According to some example embodiments, an online content managementsystem stores content and associates the content with a link to thecontent that can be distributed to one or more users. When the onlinecontent management system receives a request to access the content viathe link from a client device, the online content management systemdetermines whether the client device can access the content via thelink. This determination is based on looking up an access counter thatis associated with the link. More specifically, the online contentmanagement system compares a value of the access counter to a maximumnumber of authorized accesses.

If the online content management system determines that the clientdevice can access the content via the link, the online contentmanagement system resolves the link to the content and sends at least aportion of the content to the client device. Optionally, the onlinecontent management system can send, with the portion of the content,acknowledgement instructions for the client device to execute. Theacknowledgement instructions cause the client device to send anacknowledgement to the online content management system when one or morepresentation conditions related to the content have been satisfied atthe client device. The one or more presentation conditions can includepresenting, not simply receiving, at least the portion of the content atthe client device. This presentation can occur in the foreground or thebackground. When the online content management system receives theacknowledgement, the access counter is incremented.

System Environment

FIG. 1 depicts an example computer architecture upon which embodimentscan be implemented. Referring to FIG. 1, each of client devices 100A-Nis communicatively coupled to online content management system 102,which includes server 108 and storage 110. Each of client devices 100A-Nincludes one of client applications 104A-N.

A “computer” can be one or more physical computers, virtual computers,and/or computing devices. For example, a computer can be one or moreserver computers, cloud-based computers, cloud-based cluster ofcomputers, virtual machine instances or virtual machine computingelements such as virtual processors, storage and memory, data centers,storage devices, desktop computers, laptop computers, mobile devices,and/or any other special-purpose computing devices. A computer can be aclient and/or a server. Any reference to “a computer” herein can meanone or more computers, unless expressly stated otherwise.

Each of client devices 100A-N is a computer that acts as a client withrespect to online content management system 102. Furthermore, each ofclient devices 100A-N is authorized to access one or more user accounts.Each user account of the one or more user accounts is associated withonline content management system 102. Still further, each of clientdevices 100A-N provides an environment in which one or more clientapplications 104A-N executes.

Each of client applications 104A-N is a sequence of instructionsexecuting at one of client devices 100A-N. For example, clientapplication 104A can be a browser-based program or a native mobile app.Furthermore, each of client applications 104A-N can include instructionsfor communicating with online content management system 102 and/orsynchronizing content stored at online content management system 102with content stored at one of client devices 100A-N. For example, clientapplication 104A can include instructions for synchronizing contentstored in local storage (e.g., volatile memory, non-volatile memory) atclient device 100A with content that is associated with a particularuser account at online content management system 102. Additionally oralternatively, each of client applications 104A-N can includeclient-side script (e.g., JavaScript) for presenting (e.g., displayingin the foreground, displaying in the background) content.

Online content management system 102 includes one or more computers,such as a web server, a mobile server, a content sharing server, astorage computer, and/or a load-balancing computer. Online contentmanagement system 102 can manage content and/or user accounts. In theexample of FIG. 1, online content management system 102 includes server108 and storage 110. In some example embodiments, server 108 iscommunicatively coupled to storage 110. In some example embodiments,storage 110 is a component of server 108.

Server 108 is a computer that acts as a server with respect to one ormore client devices 100A-N. Furthermore, server 108 can facilitatecontent sharing between/among client devices 100A-N. For example, server108 can associate content with user accounts, create links to content,distribute links, determine whether a particular client device isauthorized to access a particular user account, etc.

According to one embodiment of the present invention, server 108 can becommanded by a client device to generate a shareable link toserver-stored content. For example, a user of a client device (e.g.,100A) can invoke an option presented in a graphical user interface(e.g., a web browser window or in a mobile application user interface)at the client device. The option can be for generating a shareable linkto particular server-stored content under management of the onlinecontent management service. For example, the particular server-storedcontent can be associated with a user account held with the onlinecontent management service to which the user has access.

Once generated, the server 108 returns the generated link to the clientdevice and/or provides the link to one or more designated linkrecipients. For example, the server 108 can provide the generated linkto one or more link recipient(s) designated by the user when invokingthe link generation option at the client device. The server 108 canprovide the generated link to designated link recipients via any one ormore of a number of different link providing mechanisms. For example,the server 108 can provide a generated link to a link recipient in ane-mail message, in a text message, as a push notification, etc.

If the server 108 returns the generated link to the client device, theuser of the client device can provide the generated link to one or morelink recipients. For example, the user can copy and paste the generatedlink into an e-mail message that the user sends to a link recipient.

In some example embodiments, the server 108 can return the generatedlink to the client device and/or the one or more designated linkrecipients any of a number of times in any combination. Thus, the server108 can return the generated link to the client device and the one ormore designated link recipients at the same time, at different times,and even multiple times. For example, the server 108 can send thegenerated link directly to the one or more designated link recipients.At a later time, the client device can communicate with online contentmanagement system 102 to access the generated link, which can be storedin a user account associated with online content management system 102,and send a copy of the generated link via another communication channel(e.g., an email client) at the client device. Thereafter, online contentmanagement system 102 can be requested to send the generated linkdirectly to one or more additional recipients. This can be repeated anynumber of times until the generated link is disabled.

According to some embodiments of the present invention, a generatedshareable link takes the form of a Uniform Resource Locator (URL) to theonline content management service. In this case, the shareable link cancomprise a content identifying portion that identifies the particularserver-stored content to which the shareable link refers. For example,in the following example shareable link URL, the content identifyingportion is the encoded character sequence“6ozoeyabtk6ogod/Getting%20Started.pdf” which refers to server-storedcontent named “Getting Started.pdf” associated with a particular user'saccount held with the “DROPBOX” online content management service.

https://www.dropbox.com/s/6ozoeyabtk6ogod/Getting%20Started.pdf

A shareable link can be submitted to the online content managementservice from a client device (e.g., client device 100B) by an authorizedlink submitter. Submitting a shareable link causes the online contentmanagement service to serve at least a portion of the referencedserver-stored content for presentation at the client device from whichthe link is submitted. For example, the referenced content (or a portionthereof) can be presented in a graphical user interface at the clientdevice, or the referenced server-stored content can be downloaded to theclient device.

Storage 110 stores content that can be shared between/among clientdevices 100A-N. For example, storage 110 can be a database, aconfiguration file, and/or any other system and/or data structure thatstores data. Storage 110 can include volatile and/or non-volatilememory.

Shared Content

FIG. 2 depicts an example client device. Referring to FIG. 2, clientdevice 100A is associated with link sharer 200. Client device 100Aincludes client application 104A, which includes user interface 204.Content item 202 is synchronized with data stored at online contentmanagement system 102. Synchronization can be automatic and/or via auser interface 204, such as a web browser interface, a page of a nativemobile app, etc.

Content item 202 can be a document, a file, a folder, an image, a video,and/or any other data that can be presented in a user interface 204. Forexample, content item 202 can be one or more confidential documents thatcan be displayed in a Portable Document Format (PDF).

Referring to FIG. 2, content item 202 is obtained and/or stored atclient device 100A outside of client application 104A. For example,content item 202 can be a document that is received, at client device100A, in an email attachment that is opened at client device 100A. Asanother example, content item 202 can be a file that is generated atclient device 100A and persisted to hard disk. Thus, sharing contentitem 202 can involve synchronizing content item 202 stored at clientdevice 100A with data stored at online content management system 102.For example, user interface 204 can be used to persist content item 204to storage 110 of online content management system 102 and/or associatecontent item 204 to a user account of link sharer 200.

Link sharer 200 is a user who shares content with a recipient based oncausing a link to the content to be provided to the recipient. It isunnecessary for the recipient to register a user account with onlinecontent management system 102 in order to access (e.g., simply receivedata) or view access (e.g., have data displayed in a user interface 204)the content. Link sharer 200 can send, via client device 100A, a requestfor online content management system 102 to create a link to thecontent. Online content management system 102 can generate and/or sendthe link to one or more recipients who were specified by link sharer 200in the request. Additionally or alternatively, online content managementsystem 102 can generate and/or send the link to link sharer 200, who candistribute the link to one or more recipients via email, Short MessageService (SMS), and/or any other communication channel. Thus, link sharer200 can share and/or re-share content any number of times until the linkis disabled.

Shared Links

FIG. 3 depicts an example of processing a request to create a sharedlink within an online content management system environment. Referringto FIG. 3, online content management system 102 receives request 300from client device 100A.

In the example of FIG. 3, request 300 is a request from link sharer 200for online content management system 102 to create one or more links tocontent item 202. In response, online content management system 102 cangenerate and associate the one or more links with content item 202 whichis stored at online content management system 102 (e.g., in storage 110)and/or is accessible via the user account of the link sharer 200. Inthis manner, content item 202 is associated with and is accessible viathe one or more links. Online content management system 102 and/or linksharer 200 can distribute the one or more links to one or morerecipients. Each recipient of the one or more recipients can beidentified based on an email address, an Internet Protocol (IP) address,a media access control (MAC) address, and/or any other user pseudonym.Furthermore, link sharer 200 can specify one or more options that arerelated to sharing content item 202. For example, user interface 204 caninclude a link settings screen that link sharer 200 can use to specifythat the one or more options include any of a number of differentoptions including the following:

-   -   providing link sharer 200 with a notification each time at least        a portion of content item 202 is accessed by any recipient        and/or a particular recipient of a shared link;    -   providing link sharer 200 with a notification the first time at        least a portion of content item 202 is accessed by any recipient        and/or a particular recipient of a shared link;    -   providing link sharer 200 with an aggregated notification that        indicates each time at least a portion of content item 202 has        been accessed by any recipient and/or a particular recipient of        a shared link; p1 providing link sharer 200 with a notification        each time at least a portion of content item 202 is view        accessed (e.g., presented for a predetermined length of time,        interacted with in a particular manner) by any recipient and/or        a particular recipient of a shared link;    -   providing link sharer 200 with a notification the first time at        least a portion of content item 202 is view accessed by any        recipient and/or a particular recipient of a shared link;    -   providing link sharer 200 with an aggregated notification that        indicates each time at least a portion of content item 202 has        been view accessed by any recipient and/or a particular        recipient of a shared link;    -   limiting a number of times that at least a portion of content        item 202 can be accessed by any recipient and/or a particular        recipient of a shared link;    -   limiting a number of times that at least a portion of content        item 202 can be view accessed by any recipient and/or a        particular recipient of a shared link.

Thus, the link settings screen can be used to specify one or moreauthorized recipients, one or more access/view access receipts, and/or amaximum number of accesses/view accesses for a particular link. Each ofthe one or more options can be specified independently or in conjunctionwith any other option. For example, each recipient of a particular linkcan be associated with a different maximum number of accesses/viewaccesses. As another example, notification options can be specifiedwithout limiting the number of accesses/view accesses and vice versa.

View Access Counters

FIG. 4 depicts an example online content management system. Referring toFIG. 4, online content management system 102 includes server-storedcontent item 400, link 402, view access counter 404, and association406. Server-stored content item 400 includes server-stored contentsub-items 406A-N.

In response to receiving request 300, online content management system102 creates the one or more links to content item 202. In some exampleembodiments, a single link can be generated for the one or morerecipients who were specified by link sharer 200. Alternatively, adifferent link can be generated for each recipient of the one or morerecipients who were specified by link sharer 200. In some exampleembodiments, a recipients-to-links mapping can be used to map one ormore links to one or more recipients.

Furthermore, online content management system 102 can associate the oneor more links with the one or more options specified by link sharer 200.For example, the one or more links can be associated with one or moreview access counters that limit presentation of content item 202 to apredetermined number of times. In some example embodiments, alinks-to-options mapping can be used to map a link 402 to one or moreoptions.

In some example embodiments, each link can be agnostic of particularrecipients. For example, a maximum number of accesses/view accesses canbe set based on associating an access/view access counter with a singlelink for a particular content item. Thus, online content managementsystem 102 is unconcerned with recipient identities; rather, it isconcerned with limiting a total number of accesses/view accesses. Forexample, in the case of view accesses, online content management system102 is concerned with incrementing a view access counter 404 whenever aview access event is detected. Example of view access events includepresenting all or part of content item 202 for a specified duration,navigating (e.g., scrolling) through all or part of a document, viewingsome or all content items in a folder, etc.

In some example embodiments, each link can be associated with one ormore recipients. For example, a maximum number of accesses/view accessescan be set for each recipient based on associating a recipientidentifier with an access/view access counter. In some exampleembodiments, a single link can be associated with multiple recipientsbased on a respective (recipient identifier, access/view access counter)pair that is associated with each recipient. In some exampleembodiments, each link can be associated with a different recipient, andeach link can be associated with an access/a view access counter. Here,a recipient identifier can optionally add extra security.

In the example of FIG. 4, online content management system 102 createslink 402 to server-stored content item 400. Link 402 can be a hyperlink,a Uniform Resource Locator (URL), and/or any other indirect reference toserver-stored content item 400. Server-stored content item 400 can becontent item 202 stored in server 108 and/or storage 110. Online contentmanagement system 102 creates an association 406 between link 402 andaccess/view access counter 404. In some example embodiments, an accesscounter can be a variable that tracks a number of times link 402 isaccessed, and view access counter 404 can be a variable that tracks anumber of times server-stored content item 400 is presented. Association406 can be stored as a mapping between links and access/view accesscounters. For example, association 406 can be a row in a database tablewith separate columns for links and access/view access counters. Onlinecontent management system 102 can associate an access counter or a viewaccess counter 404 with each link that is generated.

In some example embodiments, server-stored content item 400 includes aplurality of server-stored content sub-items 406A-N. For example,server-stored content item 400 can correspond to a document, and theplurality of server-stored content sub-items 406A-N can correspond topages of the document. To reference different portions of server-storedcontent item 400 with a finer level of granularity, each server-storedcontent sub-item of the plurality of server-stored content sub-items406A-N can be associated with a different identifier. The differentidentifier can be used in conjunction with link 402 to uniquely identifya particular server-stored content sub-item. For example, server-storedcontent sub-item 406A can correspond to “object #1”. If link 402corresponds to “https://www.dropbox.com/aBc123”, then server-storedcontent sub-item 406A can be referenced by the combination of“https://www.dropbox.com/aBc123” and “object #1”. Thus, a hierarchy oflinks and sub-item identifiers can correspond to a hierarchy of contentitems and content sub-items. In some example embodiments, the link andsub-item combination can be represented as a separate link, such as“https://www.dropbox.com/aBc123/object=1”.

In some example embodiments, online content management system 102associates each server-stored content sub-item with a separateaccess/view access counter. For example, a separate view access countercan be associated with each sub-item identifier. This can be useful whenserver-stored content item 400 is a folder that contains multipledocuments.

View Access Requests

FIG. 5 depicts an example view access request. Referring to FIG. 5,client device 100N obtains shared link 500 and sends view access request502 to online content management system 102.

Shared link 500 can be a link 402 that is shared with a recipientspecified by a link sharer 200. For example, shared link 500 can beincluded in an email that online content management system 102 generatesand/or sends to the recipient. When the recipient uses client device100N to interact with (e.g., click on) shared link 500, the clientdevice 100N sends an access request or a view access request 502 toonline content management system 102.

In some example embodiments, access/view access request 502 identifiesshared link 500. For example, view access request 502 can include sharedlink 500. Online content management system 102 can then resolve sharedlink 500 to server-stored content item 400 based on a mapping betweenlinks and content items. Additionally or alternatively, access/viewaccess request 502 can include a recipient identifier.

View Access Authorization

In response to receiving access/view access request 502, online contentmanagement system 102 determines whether access/view access request 502is authorized based on identifying an access counter or a view accesscounter 404 that is associated with a particular shared link. Thisidentification can be based on any of a number of mappings that includeaccess/view access counters. FIG. 6 depicts an example mapping betweenlinks and view access counters. Referring to FIG. 6, mapping 600includes columns for links 602, view access counters 604, and maximumnumber of authorized view accesses 606 (hereinafter “maximum 606”). Thecolumn for links 602 includes shared link 500 and shared link 608.Mapping 600 further includes rows for shared link 500 and shared link608.

In the example of FIG. 6, mapping 600 maps links 602 to view accesscounters 604. For example, shared link 500 is mapped to a view accesscounter 404 that has a value of zero. The value of an access counter ora view access counter 404 can be modified based on an appropriatecommand, such as a Structured Query Language (SQL) database statement.Mapping 600 can map links 602 and/or access/view access counters 604 toother information, such as maximum 606 that was specified by link sharer200 in the one or more options related to sharing content item 202.Thus, authorization of access/view access requests can be determinedbased on comparing values of access/view access counters 604 to valuesof maximum 606.

In some example embodiments, an authorization determination can be basedon a recipients-to-access/view-access-counters mapping. In other words,mapping 600 can map access/view access counters 604 to recipientidentifiers, such as email addresses or other user pseudonyms. Thus,access/view access counters 604 can be configured on a per-user basis.

View Access Acknowledgements

FIG. 7 depicts an example data exchange that follows access/view accessauthorization. Referring to FIG. 7, online content management system 102sends portion of server-stored content item 700 along with instructions702 to client device 100N. Client device 100N sends acknowledgement 704indicating satisfied presentation conditions 706 to online contentmanagement system 102.

Online content management system 102 can send at least a portion ofserver-stored content item 700 (hereinafter “portion 700”) to a clientdevice 100N that is associated with an authorized access/view accessrequest. In some example embodiments, server-stored content item 400 isdivided into a number of portions prior to being transmitted. Forexample, the portions can correspond to server-stored content sub-items406A-N, data packets, etc.

Online content management system 102 can also send instructions 702 to aclient device 100N that is associated with an authorized access/viewaccess request. Instructions 702 can be sent prior to, concurrentlywith, or subsequent to a transmission of portion 700. In the example ofFIG. 7, portion 700 includes instructions 702.

Instructions 702 are executed at the client device 100N that isassociated with the authorized access/view access request. When theclient device 100N executes instructions 702, the client device 100Nsends acknowledgement 704 to online content management system 102.Instructions 702 can be a callback function, a remote procedure call, orany other sequence of code that causes sending acknowledgement 704 toonline content management system 102.

Acknowledgement 704 provides an indication that one or more presentationconditions with respect to server-stored content item 400 have beensatisfied at the client device 100N. For example, at least onepresentation condition of the one or more presentation conditions can bethat at least portion 700 is presented at the client device 100N in auser interface 204.

When online content management system 102 receives acknowledgement 704from the client device 100N, online content management system 102increments access/view access counter 404 that is associated with sharedlink 500. For example, a database command can be used to modify mapping600 such that view access counter 404 has a value of “1” instead of “0”.

FIG. 8 depicts a detailed view of an example acknowledgement sent to anonline content management system. Referring to FIG. 8, acknowledgement704 includes satisfied presentation conditions 706, user pseudonym 804,identification of accessed content 806, and content consumption time808. Satisfied presentation conditions 706 further include presentationfor predetermined length of time in foreground or background 800(hereinafter “presentation 800”) and received indication of interaction802.

As mentioned above, satisfied presentation conditions 706 can includepresentation, not merely receipt, of at least portion 700 at the clientdevice 100N. Information regarding satisfied presentation conditions 706can be collected at the client device 100N based on client-side scripts.For example, acknowledgement 704 can indicate that at least portion 700was fully loaded and/or displayed at the client device 100N.Significantly, this avoids prematurely incrementing view access counter404.

Additionally or alternatively, satisfied presentation conditions 706 caninclude presentation 800. In other words, acknowledgement 704 canindicate that at least portion 700 was presented at the client device100N for a predetermined length of time either in the foreground or thebackground. For example, an arbitrary length of time (e.g., ten seconds)can be used to ensure that a recipient has an adequate opportunity toconsume server-stored content item 400. This arbitrary length of timecan be computed regardless of whether server-stored content item 400 isbeing presented in an active or passive window.

Additionally or alternatively, satisfied presentation conditions 706 caninclude received indication of interaction 802. In other words,acknowledgement 704 can indicate that a recipient interacted with atleast portion 700 at the client device 100N and that an indication ofsuch an interaction was received at the client device 100N. For example,the interaction can include a scrolling action, a clicking action,and/or any other action related to navigating at least portion 700. Insome example embodiments, the interaction can include confirmation thata recipient is finished consuming at least portion 700. The confirmationcan be received in response to a user prompt that is presented at theclient device 100N. The user prompt can be presented automatically whenthe end (e.g., signified by an end-of-file marker) of at least portion700 has been reached.

In some example embodiments, acknowledgement 704 can include userpseudonym 804. In other words, acknowledgement 704 can identify arecipient who accessed/view accessed at least portion 700 at the clientdevice 100N. For example, acknowledgement 704 can include the emailaddress to which shared link 500 was sent.

In some example embodiments, acknowledgement 704 can includeidentification of accessed content 806. In other words, acknowledgement704 can identify one or more portions of server-stored content item 400that were accessed/view accessed at the client device 100N. For example,acknowledgement 704 can include shared link 500 and/or any identifiersthat can be resolved to at least portion 700.

In some example embodiments, acknowledgement 704 can include contentconsumption time 808. In other words, acknowledgement 704 can indicate alength of time spent consuming at least portion 700 at the client device100N. For example, acknowledgement 704 can include a length of timecomputed by a client-side script that marked the system time whendisplay was initiated and when display was terminated.

In response to receiving acknowledgement 704, online content managementsystem 102 can increment access/view access counter 404 and associate anotification including at least a portion of acknowledgement 704 with auser account of link sharer 200. FIG. 9 depicts an example notificationassociated with a link sharer's account, which is a user account of linksharer 200. Referring to FIG. 9, online content management system 102associates notification 902 with link sharer's account 900. Thereafter,notification 902 is accessible via link sharer's account 900. Forexample, if client device 100A is associated with link sharer's account900, notification 902 can be forwarded to client device 100A.Additionally or alternatively, notification 902 can be presented to linksharer 200 based on accessing link sharer's account 900. In other words,notification 902 can be stored at online content management system 102and can be accessed via link sharer's account 900.

As mentioned above, link sharer 200 can specify that the one or moreoptions related to sharing content item 202 include providing linksharer 200 with confirmation (e.g., an access receipt, a view receipt)that content item 202 was accessed or presented at one or more clientdevices 100A-N. Thus, online content management system 102 can providelink sharer 200 with at least some information included inacknowledgement 704. For example, link sharer 200 can be provided withuser pseudonym 804, identification of accessed content 806, and/orcontent consumption time 808. This information can be stored at onlinecontent management system 102 in association with link sharer's account900.

Process Overview

FIG. 10 is a flow diagram that depicts an approach for managing access,including view access, to shared content. At block 1000, online contentmanagement system 102 receives a view access request 502 from a clientdevice 100N. The view access request 502 can include a shared link 500to a server-stored content item 400. Prior to block 1000, client device100N received the shared link 500 from online content management system102, which created the shared link 500 and associated it with a viewaccess counter 404.

At block 1002, online content management system 102 determines whetherthe view access request 502 is authorized. This determination can bebased on identifying the view access counter 404 that is associated withat least the shared link 500 and comparing the view access counter 404to a maximum number of authorized view accesses 606. If the view accessrequest 502 is authorized, block 1002 proceeds to block 1004. Otherwise,block 1002 proceeds to block 1012.

At block 1004, online content management system 102 resolves the sharedlink 500 to the server-stored content item 400. Block 1004 can beperformed prior to, concurrently with, or subsequent to block 1002.

At block 1006, online content management system 102 sends at least aportion 700 of the server-stored content item 400 to the client device100N. At least the portion 700 can be displayed at the client device100N based on one or more client-side scripts. The one or moreclient-side scripts can discourage and/or prevent unauthorizedduplication of the server-stored content item 400. For example, the oneor more client-side scripts can disable printing, cause cached data toexpire quickly, and/or cause consumption of the server-stored contentitem 400 to be interrupted when selection of a screenshot key isdetected. Interrupting consumption of the server-stored content item 400can include content redaction, minimizing a view window, closing theview window, superimposing another view window on the view window,and/or any other techniques for obscuring display of the server-storedcontent item 400.

Online content management system 102 also sends instructions 702 to theclient device 100N. The instructions 702 cause the client device 100N tosend an acknowledgement 704 that one or more presentation conditionshave been satisfied. The one or more presentation conditions can includepresenting at least the portion 700 to a recipient, presenting at leastthe portion 700 for a predetermined length of time, and/or receiving anindication that the recipient interacted with at least the portion 700.

At block 1008, online content management system 102 receives theacknowledgement 704. The acknowledgement 704 can identify the recipientwho accessed/view accessed at least the portion 700, identify one ormore portions of the server-stored content item 400 that were presented,and/or indicate a length of time during which the recipient consumed atleast the portion 700.

At block 1010, online content management system 102 increments the viewaccess counter 404 that is associated with at least the shared link 500.If the view access counter 404 is incremented to a value that is greaterthan or equal to the maximum number of authorized view accesses 606, theshared link 500 can be said to have expired. In other words, furtherview access requests related to the shared link 500 will be determinedto be unauthorized.

At block 1012, online content management system 102 denies any viewaccess requests that are determined to be unauthorized. For example,online content management system 102 can cause the client device 100N todisplay a message indicating that the shared link 500 has expired.

Basic Computing Device

Referring now to FIG. 11, it is a block diagram that illustrates a basiccomputing device 1100 in which the example embodiment(s) of the presentApplication may be embodied. Computing device 1100 and its components,including their connections, relationships, and functions, is meant tobe exemplary only, and not meant to limit implementations of the exampleembodiment(s). Other computing devices suitable for implementing theexample embodiment(s) may have different components, includingcomponents with different connections, relationships, and functions.

Computing device 1100 may include a bus 1102 or other communicationmechanism for addressing main memory 1106 and for transferring databetween and among the various components of device 1100.

Computing device 1100 may also include one or more hardware processors1104 coupled with bus 1102 for processing information. A hardwareprocessor 1104 may be a general purpose microprocessor, a system on achip (SoC), or other processor.

Main memory 1106, such as a random access memory (RAM) or other dynamicstorage device, also may be coupled to bus 1102 for storing informationand software instructions to be executed by processor(s) 1104. Mainmemory 1106 also may be used for storing temporary variables or otherintermediate information during execution of software instructions to beexecuted by processor(s) 1104.

Software instructions, when stored in storage media accessible toprocessor(s) 1104, render computing device 1100 into a special-purposecomputing device that is customized to perform the operations specifiedin the software instructions. The terms “software”, “softwareinstructions”, “computer program”, “computer-executable instructions”,and “processor-executable instructions” are to be broadly construed tocover any machine-readable information, whether or not human-readable,for instructing a computing device to perform specific operations, andincluding, but not limited to, application software, desktopapplications, scripts, binaries, operating systems, device drivers, bootloaders, shells, utilities, system software, JAVASCRIPT, web pages, webapplications, plugins, embedded software, microcode, compilers,debuggers, interpreters, virtual machines, linkers, and text editors.

Computing device 1100 also may include read only memory (ROM) 1108 orother static storage device coupled to bus 1102 for storing staticinformation and software instructions for processor(s) 1104.

One or more mass storage devices 1110 may be coupled to bus 1102 forpersistently storing information and software instructions on fixed orremovable media, such as magnetic, optical, solid-state,magnetic-optical, flash memory, or any other available mass storagetechnology. The mass storage may be shared on a network, or it may bededicated mass storage. Typically, at least one of the mass storagedevices 1110 (e.g., the main hard disk for the device) stores a body ofprogram and data for directing operation of the computing device,including an operating system, user application programs, driver andother support files, as well as other data files of all sorts.

Computing device 1100 may be coupled via bus 1102 to display 1112, suchas a liquid crystal display (LCD) or other electronic visual display,for displaying information to a computer user. In some configurations, atouch sensitive surface incorporating touch detection technology (e.g.,resistive, capacitive, etc.) may be overlaid on display 1112 to form atouch sensitive display for communicating touch gesture (e.g., finger orstylus) input to processor(s) 1104.

An input device 1114, including alphanumeric and other keys, may becoupled to bus 1102 for communicating information and command selectionsto processor 1104. In addition to or instead of alphanumeric and otherkeys, input device 1114 may include one or more physical buttons orswitches such as, for example, a power (on/off) button, a “home” button,volume control buttons, or the like.

Another type of user input device may be a cursor control 1116, such asa mouse, a trackball, or cursor direction keys for communicatingdirection information and command selections to processor 1104 and forcontrolling cursor movement on display 1112. This input device typicallyhas two degrees of freedom in two axes, a first axis (e.g., x) and asecond axis (e.g., y), that allows the device to specify positions in aplane.

While in some configurations, such as the configuration depicted in FIG.11, one or more of display 1112, input device 1114, and cursor control1116 are external components (i.e., peripheral devices) of computingdevice 1100, some or all of display 1112, input device 1114, and cursorcontrol 1116 are integrated as part of the form factor of computingdevice 1100 in other configurations.

Functions of the disclosed systems, methods, and modules may beperformed by computing device 1100 in response to processor(s) 1104executing one or more programs of software instructions contained inmain memory 1106. Such software instructions may be read into mainmemory 1106 from another storage medium, such as storage device(s) 1110.Execution of the software instructions contained in main memory 1106cause processor(s) 1104 to perform the functions of the exampleembodiment(s).

While functions and operations of the example embodiment(s) may beimplemented entirely with software instructions, hard-wired orprogrammable circuitry of computing device 1100 (e.g., an ASIC, a FPGA,or the like) may be used in other embodiments in place of or incombination with software instructions to perform the functions,according to the requirements of the particular implementation at hand.

The term “storage media” as used herein refers to any non-transitorymedia that store data and/or software instructions that cause acomputing device to operate in a specific fashion. Such storage mediamay comprise non-volatile media and/or volatile media. Non-volatilemedia includes, for example, non-volatile random access memory (NVRAM),flash memory, optical disks, magnetic disks, or solid-state drives, suchas storage device 1110. Volatile media includes dynamic memory, such asmain memory 1106. Common forms of storage media include, for example, afloppy disk, a flexible disk, hard disk, solid-state drive, magnetictape, or any other magnetic data storage medium, a CD-ROM, any otheroptical data storage medium, any physical medium with patterns of holes,a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, flash memory, any othermemory chip or cartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 1102. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more software instructions to processor(s) 1104 for execution.For example, the software instructions may initially be carried on amagnetic disk or solid-state drive of a remote computer. The remotecomputer can load the software instructions into its dynamic memory andsend the software instructions over a telephone line using a modem. Amodem local to computing device 1100 can receive the data on thetelephone line and use an infra-red transmitter to convert the data toan infra-red signal. An infra-red detector can receive the data carriedin the infra-red signal and appropriate circuitry can place the data onbus 1102. Bus 1102 carries the data to main memory 1106, from whichprocessor(s) 1104 retrieves and executes the software instructions. Thesoftware instructions received by main memory 1106 may optionally bestored on storage device(s) 1110 either before or after execution byprocessor(s) 1104.

Computing device 1100 also may include one or more communicationinterface(s) 1118 coupled to bus 1102. A communication interface 1118provides a two-way data communication coupling to a wired or wirelessnetwork link 1120 that is connected to a local network 1122 (e.g.,Ethernet network, Wireless Local Area Network, cellular phone network,Bluetooth wireless network, or the like). Communication interface 1118sends and receives electrical, electromagnetic, or optical signals thatcarry digital data streams representing various types of information.For example, communication interface 1118 may be a wired networkinterface card, a wireless network interface card with an integratedradio antenna, or a modem (e.g., ISDN, DSL, or cable modem).

Network link(s) 1120 typically provide data communication through one ormore networks to other data devices. For example, a network link 1120may provide a connection through a local network 1122 to a host computer1124 or to data equipment operated by an Internet Service Provider (ISP)1126. ISP 1126 in turn provides data communication services through theworld wide packet data communication network now commonly referred to asthe “Internet” 1128. Local network(s) 1122 and Internet 1128 useelectrical, electromagnetic or optical signals that carry digital datastreams. The signals through the various networks and the signals onnetwork link(s) 1120 and through communication interface(s) 1118, whichcarry the digital data to and from computing device 1100, are exampleforms of transmission media.

Computing device 1100 can send messages and receive data, includingprogram code, through the network(s), network link(s) 1120 andcommunication interface(s) 1118. In the Internet example, a server 1130might transmit a requested code for an application program throughInternet 1128, ISP 1126, local network(s) 1122 and communicationinterface(s) 1118.

The received code may be executed by processor 1104 as it is received,and/or stored in storage device 1110, or other non-volatile storage forlater execution.

Basic Software System

FIG. 12 is a block diagram of a basic software system 1200 that may beemployed for controlling the operation of computing device 1100.Software system 1200 and its components, including their connections,relationships, and functions, is meant to be exemplary only, and notmeant to limit implementations of the example embodiment(s). Othersoftware systems suitable for implementing the example embodiment(s) mayhave different components, including components with differentconnections, relationships, and functions.

Software system 1200 is provided for directing the operation ofcomputing device 1100. Software system 1200, which may be stored insystem memory (RAM) 1106 and on fixed storage (e.g., hard disk or flashmemory) 1110, includes a kernel or operating system (OS) 1210.

The OS 1210 manages low-level aspects of computer operation, includingmanaging execution of processes, memory allocation, file input andoutput (I/O), and device I/O. One or more application programs,represented as 1202A, 1202B, 1202C . . . 1202N, may be “loaded” (e.g.,transferred from fixed storage 1110 into memory 1106) for execution bythe system 1200. The applications or other software intended for use ondevice 1200 may also be stored as a set of downloadablecomputer-executable instructions, for example, for downloading andinstallation from an Internet location (e.g., a Web server, an appstore, or other online service).

Software system 1200 includes a graphical user interface (GUI) 1215, forreceiving user commands and data in a graphical (e.g., “point-and-click”or “touch gesture”) fashion. These inputs, in turn, may be acted upon bythe system 1200 in accordance with instructions from operating system1210 and/or application(s) 1202. The GUI 1215 also serves to display theresults of operation from the OS 1210 and application(s) 1202, whereuponthe user may supply additional inputs or terminate the session (e.g.,log off).

OS 1210 can execute directly on the bare hardware 1220 (e.g.,processor(s) 1104) of device 1100. Alternatively, a hypervisor orvirtual machine monitor (VMM) 1230 may be interposed between the barehardware 1220 and the OS 1210. In this configuration, VMM 1230 acts as asoftware “cushion” or virtualization layer between the OS 1210 and thebare hardware 1220 of the device 1100.

VMM 1230 instantiates and runs one or more virtual machine instances(“guest machines”). Each guest machine comprises a “guest” operatingsystem, such as OS 1210, and one or more applications, such asapplication(s) 1202, designed to execute on the guest operating system.The VMM 1230 presents the guest operating systems with a virtualoperating platform and manages the execution of the guest operatingsystems.

In some instances, the VMM 1230 may allow a guest operating system torun as if it is running on the bare hardware 1220 of device 1100directly. In these instances, the same version of the guest operatingsystem configured to execute on the bare hardware 1220 directly may alsoexecute on VMM 1230 without modification or reconfiguration. In otherwords, VMM 1230 may provide full hardware and CPU virtualization to aguest operating system in some instances.

In other instances, a guest operating system may be specially designedor configured to execute on VMM 1230 for efficiency. In these instances,the guest operating system is “aware” that it executes on a virtualmachine monitor. In other words, VMM 1230 may providepara-virtualization to a guest operating system in some instances.

The above-described basic computer hardware and software is presentedfor purpose of illustrating the basic underlying computer componentsthat may be employed for implementing the example embodiment(s). Theexample embodiment(s), however, are not necessarily limited to anyparticular computing environment or computing device configuration.Instead, the example embodiment(s) may be implemented in any type ofsystem architecture or processing environment that one skilled in theart, in light of this disclosure, would understand as capable ofsupporting the features and functions of the example embodiment(s)presented herein.

Extensions And Alternatives

In the foregoing specification, the example embodiment(s) of the presentApplication have been described with reference to numerous specificdetails. However, the details may vary from implementation toimplementation according to the requirements of the particular implementat hand. The example embodiment(s) are, accordingly, to be regarded inan illustrative rather than a restrictive sense.

1. A method, comprising: at one or more computing devices comprising oneor more processors and memory storing one or more computer programsexecuted by the one or more processors to perform the method, performingoperations comprising: receiving, over a data network, a request toaccess a server-stored content item, the request comprising a sharedlink to the server-stored content item, the request sent by a clientdevice; based on a current value of an access counter for the sharedlink, sending, over a data network, at least a portion of theserver-stored content item for a presentation of at least the portion ofthe server-stored content item at the client device; sending, over adata network, instructions for verifying a user interaction condition atthe client device; wherein the instructions are configured to send, overa data network, an acknowledgement, if the user interaction condition isverified; wherein the user interaction condition is a user of the clientdevice navigating the presentation of at least the portion of theserver-stored content item with user input; and based on receiving theacknowledgement, incrementing the access counter for the shared link. 2.The method of claim 1, wherein the user interaction condition is a userof the client device scrolling the presentation of at least the portionof the server-stored content item with user input.
 3. The method ofclaim 1, wherein the user interaction condition is a user of the clientdevice clicking on the presentation of at least the portion of theserver-stored content item with user input.
 4. The method of claim 1,wherein verifying the user interaction condition comprises presenting auser prompt at the client device.
 5. The method of claim 1, wherein theuser interaction condition is a user of the client device scrolling thepresentation of at least the portion of the server-stored content itemwith user input until an end-of-file marker for at least the portion ofthe server-stored content item is reached.
 6. The method of claim 1,further comprising: receiving, over a data network, a request to createthe shared link to the server-stored content item; creating the sharedlink based on the receiving the request to create the shared link; andprior to the receiving the request to access the server-stored contentitem, associating the access counter with the shared link.
 7. The methodof claim 1, further comprising sending, over a data network, a currentvalue of the access counter for presentation at a client device.
 8. Themethod of claim 1, wherein the sending, over the data network, at leastthe portion of the server-stored content item for the presentation of atleast the portion of the server-stored content item at the client deviceis based on the current value of the access counter being below amaximum number of authorized accesses for the shared link.
 9. The methodof claim 1, wherein the acknowledgement identifies a particular portionof the server-stored content item that is interacted with.
 10. Themethod of claim 1, wherein the access counter is specific to the sharedlink and independent of the server-stored content item to which theshared link refers.
 11. A system, comprising: storage media; one or moreprocessors; and one or more programs stored in the storage media andconfigured for execution by the one or more processors, the one or moreprograms comprising a sequence of instructions for performing operationscomprising: receiving, over a data network, a request to access aserver-stored content item, the request comprising a shared link to theserver-stored content item, the request sent by a client device; basedon a current value of an access counter for the shared link, sending,over a data network, at least a portion of the server-stored contentitem for a presentation of at least the portion of the server-storedcontent item at the client device; sending, over a data network,instructions for verifying a user interaction condition at the clientdevice; wherein the instructions are configured to send, over a datanetwork, an acknowledgement, if the user interaction condition isverified; wherein the user interaction condition is a user of the clientdevice navigating the presentation of at least the portion of theserver-stored content item with user input; and based on receiving theacknowledgement, incrementing the access counter for the shared link.12. The system of claim 11, wherein the user interaction condition is auser of the client device scrolling the presentation of at least theportion of the server-stored content item with user input.
 13. Thesystem of claim 11, wherein the user interaction condition is a user ofthe client device clicking on the presentation of at least the portionof the server-stored content item with user input.
 14. The system ofclaim 11, wherein verifying the user interaction condition comprisespresenting a user prompt at the client device.
 15. The system of claim11, wherein the user interaction condition is a user of the clientdevice scrolling the presentation of at least the portion of theserver-stored content item with user input until an end-of-file markerfor at least the portion of the server-stored content item is reached.16. The system of claim 11, further comprising: receiving, over a datanetwork, a request to create the shared link to the server-storedcontent item; creating the shared link based on the receiving therequest to create the shared link; and prior to the receiving therequest to access the server-stored content item, associating the accesscounter with the shared link.
 17. The system of claim 11, furthercomprising sending, over a data network, a current value of the accesscounter for presentation at a client device.
 18. The system of claim 11,wherein the sending, over the data network, at least the portion of theserver-stored content item for the presentation of at least the portionof the server-stored content item at the client device is based on thecurrent value of the access counter being below a maximum number ofauthorized accesses for the shared link.
 19. The system of claim 11,wherein the acknowledgement identifies a particular portion of theserver-stored content item that is interacted with.
 20. The system ofclaim 11, wherein the access counter is specific to the shared link andindependent of the server-stored content item to which the shared linkrefers.